{"componentChunkName":"component---src-templates-blog-post-js","path":"/Authentication and Authorization/","webpackCompilationHash":"fbb20c27e610daab547e","result":{"data":{"site":{"siteMetadata":{"title":"Articles","author":"Aman-Sharma"}},"markdownRemark":{"id":"752ebb80-93a2-54a0-9ab4-757fdba8bdff","excerpt":"If We Are Having Some Protected Routes That Provides Resources and Informational Data To User Without Authentication And Authorization Then There Will Be…","html":"

If We Are Having Some Protected Routes That Provides Resources and Informational Data To User Without Authentication And Authorization Then There Will Be Compromise With The Sensitive Information That’s Why We Implemented The Auth Part To Protect Our Application

\n

Using The Jwt Tokens To Making The Protected Routes:-

\n

Jwt Is Called JsonWebToken Which Generates The Json Token.When The Client Side Information Comes To Server The Mongodb Database Verifies The Information Then The Jwt Comes In Play To Generate The Token.

\n

Example:-

\n

var token = auth.generateToken({userid: user._id})

\n

Here We Are Generating The Token By Using The Jwt It Takes a Parameter Which Can Be Used for Generating The Token.That Parameter Is Either The User _id Provided By The Mongodb Or The Username

\n

Now Using The Jwt Token For Making Our Route Protected:-

\n

To Making The Route Protected We Just Have To Implemented That Token based Authentication In Our Route So When Someone Passes Through Our Route He Just Have\nTo Passed Through The Middleware Which Verifies That The Particular User Is having Token Or Not If It Is Having The Token Then He Will Be Able To Access The Particular Route Otherwise Not.\nExample:-

\n
//protectedRoute\nrouter.get(\"/users\", auth.verifyToken, (req, res) => {\n  UserModel.find({}, (err, users) => {\n    if (err) res.json({ Error: ErrorFounded })\n    res.json({ users: users })\n  })\n})
\n

By This Way We Can Protect Our Any Route By using The jwt Authentication.

\n

Middleware Which Can Generates The Token And Verifies The Token:-

\n
//requring the token\nvar jwt = require(\"jsonwebtoken\")
\n
//generating the middleware for token generating\nmodule.exports.generateToken = function(payload) {\n  return jwt.sign(payload, \"abcdef\")\n}
\n
//generating the verify middleware\nmodule.exports.verifyToken = function(req, res, next) {\n  var token = req.headers.authorization || \"\"\n  if (token) {\n    jwt.verify(token, \"abcdef\", (err, decoded) => {\n      // console.log(decoded)\n      if (err) res.json({ token: \"notVerify\" })\n      next()\n    })\n  } else {\n    return res.json({ token: \"notFound\" })\n  }\n}
\n

Any Request Comes To A Particular Route It Must Have To Be Passes Through It\nThat’s How Whole Authentication AndAuthorization Works.

","frontmatter":{"title":"Authentication and Authorization","date":"December 10, 2019","description":" Explanations of Authentication and Authorization "}}},"pageContext":{"isCreatedByStatefulCreatePages":false,"slug":"/Authentication and Authorization/","previous":{"fields":{"slug":"/React-Redux /"},"frontmatter":{"title":"React Redux"}},"next":{"fields":{"slug":"/Flow Of Fullstack Application(MERN)/"},"frontmatter":{"title":"Fullstack Application Work Flow (MERN)"}}}}}